Story Card Maturity Model (SMM): A Process Improvement Framework for Agile Requirements Engineering Practices
نویسندگان
چکیده
This paper describes an ongoing process to define a suitable process improvement model for story cards based requirement engineering process and practices at agile software development environments. Key features of the SMM (Story card Maturity Model) process are: solves the problems related to the story cards like requirements conflicts, missing requirements, ambiguous requirements, define standard structure of story cards, to address nonfunctional requirements from exploration phase, and the use of a simplified and tailored assessment method for story cards based requirements engineering practices based on the CMM, which is poorly addressed at CMM. CMM does not cover how the quality of the requirements engineering process should be secured or what activities should be present for the requirements engineering process to achieve a certain maturity level. It is difficult to know what is not addressed or what could be done to improve the process. We also presents how can be the identified areas of improvement from assessment can be mapped with best knowledge based story cards practices for agile software development environments.
منابع مشابه
Story Card Based Agile Software Development
The use of story cards for user stories in many Extreme Programming software development projects has been widespread. Several popular traditional methods for story cards (e.g., Cohen M, Kent B) have been used in successful fashion at some extent, but all lack of the powerful features for story cards guidelines, right sort of information on story cards and quality of user stories on story cards...
متن کاملStretching Agile to fit CMMI Level 3 - the story of creating MSF for CMMI Process Improvement at Microsoft Corporation
Agile practitioners pride themselves on highly productive, responsive, low ceremony, lightweight, tacit knowledge processes with little waste, adaptive planning and frequent iterative delivery of value. It is often assumed that CMMI compliant processes need to be heavyweight, bureaucratic, slow moving, high ceremony and plan driven. Agile developers often skeptically perceive formal process imp...
متن کاملExperimenting a Requirements Engineering Process Based on Rational Unified Process (RUP) Reaching Capability Maturity Model Integration (CMMI) Maturity Level 3 and Considering the Use of Agile Methods Practices
This work has the purpose of describing a software development process with the following characteristics: its scope lies within the requirements engineering activities; it fulfills CMMI requisites for Requirements Management and Requirements Development process areas (maturity level 2 and 3, respectively); it is based on RUP practices and activities where possible practices of agile methods ar...
متن کاملProgressive Outcomes: A framework for maturing in agile software development
Maturity models are used to guide improvements in the software engineering field and a number of maturity models for agile methods have been proposed in the last years. These models differ in their underlying structure prescribing different possible paths to maturity in agile software development, neglecting the fact that agile teams struggle to follow prescribed processes and practices. Our ob...
متن کاملTowards an Agile Process Maturity Model
Agile Methods are a widely applied and feasible alternative to Tayloristic (traditional) Methods for developing high-quality software on a limited schedule. Although Agile Methods are been adopted by various organizations, there still does not exist a well disseminated process maturity model that can satisfactorily guide the improvement and assess the status of agile processes. Currently, there...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
عنوان ژورنال:
- JSW
دوره 4 شماره
صفحات -
تاریخ انتشار 2009